Using One Step at a Time Configuration

This section describes each configuration step shown in the One step configuration section. If you have executed the One step configuration, then you do not need to execute the scripts described in this section.

Configuring the Environment

You can find the environment configuration script in %TAFJ_HOME% \appserver\was\jython\ environmentConfiguration.py. This script helps you to set the TAFJ_HOME, ORACLE_TAFJ_JDBC_DRIVER_PATH, T24_MODELBANK_SHAREDLIB, TAFJ shared libraries, and -Dtafj.home properties.

Before running the script, you should define the parameters such as node, cell and server name to set the scope of the configuration, tafjHome and t24Home to specify the environment variable values. To do so edit the file available at %TAFJ_HOME%\appserver\was\jython\ tafj.py and set the following properties:

  • cell_name="localhostNode01Cell"
  • node_name="localhostNode01"
  • server_name="server1"
  • tafjHome="C:/product/appserver/websphere/TAFJ"
  • t24Home="C:/product/appserver/websphere/T24"
TIPS: To find your cell_name, go to WAS_HOME/${PROFILE_NAME}/config/cells.  This directory holds your cell name. If you go under this directory and then the nodes directory, you will find your node name.

Multiple Profiles

If you have multiple profiles defined and if you want to execute the scripts against a profile, which is not the default one, then you will have to add the profile name to the command below.

-profileName %PROFILE_NAME%

Enabling Security

Procedure

  1. Execute the script by enabling the admin console security. This will allow you to enter the admin user name and password through:
    • System prompt
    • The -user %ADMIN_USER_NAME% -password %ADMIN_USER_PASSWORD% command.
  1. Launch the following command from the command line:%WAS_HOME%\bin\ wsadmin -lang jython -f  environmentConfiguration.py

  2. Browse the administrative console to check if the following configurations are correct:
  • Environment > WebSphere variables
  • Environment > Shared Libraries
  • Server > Server Type > WebSphere application servers > #profileName# > (Server infrastructure)  Java and Process Management > Process definition > Java Virtual Machine
  • Generic JVM arguments:  -Dtafj.home= %TAFJ_HOME%

    Example: -Dtafj.home= /opt/wasapps/TAFJ

Configuring JMS Resources

To configure JMS resources, you need to run the script located at %TAFJ_HOME% \appserver\was\jython\ jmsConfiguration.py. This will create:

  • A service integration and add a bus member
  • A JMS connection factory
  • JMS Queues
  • A JMS topic
  • Activation specifications

Before running it, you have to define parameters such as node, cell and server name to set the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file.

Procedure

  1. Launch the following command in the command line (refer to Configuring the Environment section for additional command parameters):

    2. %WAS_HOME%\bin\wsadmin -lang jython -f   jmsConfiguration.py

  2. Browse the administrative console to check if this step is correctly done.
  3. Click Service integration > Buses. You should see T24Bus.

    Messaging engines status (under Buses >T24 Bus > Messaging engines) should automatically be  (Started).

  4. Check if connection factory was created.

  5. Check if activation specs were created.

  6. Check if queues were created.

  7. Check if topics were created.

Configuring JDBC Resources

This section describes the configuration of Temenos Transact Oracle, DB2 and MSSQL databases.

ClosedConfiguring Temenos Transact Oracle 11g Database

When you setup the datasource you have to use the drivers provide by the database. The %TAFJ_HOME%\DBDrivers is just a helper. The script is located at %TAFJ_HOME% \appserver\was\jython\ ORACLEConfiguration.py

NOTE: There is no guarantee that the drivers provided with TAFJ will work for all database versions.

On execution, the ORACLEConfiguration.py script creates:

  • The Temenos Transact Manager Database Credentials
  • A JDBC Provider for TAFJ
  • A datasource for TAFJ

Before running it you have to define some parameters such as node, cell and server name to set the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file.  You must also define the following properties to identify your Oracle database and provide a user id and password for authentication. That is:

dbDriver="oracle-12c"

dbHostName="172.16.22.102"

dbPort="1521"

dbName="MB2013"

dbUser="mbtafj"

dbPwd="mbtafj"    

Procedure

  1. Launch the following command in the command line.

    2. %WAS_HOME%\bin\ wsadmin -lang jython -f  ORACLEConfiguration.py

  2. Browse the administrative console to check if this step is correctly done.
    3. NOTE: The property dbPwd is not correctly set, you have to run the administrative console to re-enter it manually as shown below.
  3. Click Security > Global security > Java Authentication and Authorization Service > J2C authentication data and specify Alias as Temenos Transact database, User ID and Password.

  4. Click OK.

  5. Click Apply > Save.
ClosedConfiguring Temenos Transact DB2 Database

You can find the script in %TAFJ_HOME% \appserver\was\jython\ DB2Configuration.py. On execution, it creates:

  • The Temenos Transact DB2 Database Credentials
  • A JDBC Provider for TAFJ
  • A datasource for TAFJ

Before running it you have to define some parameters such as node, cell and server name to set the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file.  You must also define the following properties to identify your DB2 database and provide a user id and password for authentication. That is:

dbDriver="db2_v10.1"

dbHostName="localhost"

dbPort="50000"

dbDriverType="4"

dbName="MB2013"

dbUser="mbtafj"

dbPwd="mbtafj"    

Procedure

  1. Launch the following command in the command line.

    2. %WAS_HOME%\bin\ wsadmin -lang jython -f  DB2Configuration.py

  2. Browse the administrative console to check this step is correctly done.
    3. NOTE: The property dbPwd is not correctly set, you have to run the administrative console to re-enter it manually as shown below.
  3. Click Security > Global security > Java Authentication and Authorization Service > J2C authentication data and specify Alias as Temenos Transact database DB2, User ID and Password.

  4. Click OK.

  5. Click Apply > Save.
ClosedConfiguring Temenos Transact MSSQL Database

You can find the script in %TAFJ_HOME% \appserver\was\jython\ MSSQLConfiguration.py. On execution, it creates:

  • The Temenos Transact MSSQL Database Credentials
  • A JDBC Provider for TAFJ
  • A datasource for TAFJ

Before running it you have to define some parameters such as node, cell and server name to set the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file.  You must also define the following properties to identify your DB2 database and provide a user id and password for authentication. That is:

dbDriver="sqljdbc_1.2"

dbServerName="localhost"

dbPort="1433"

dbName="R14DB"

dbUser="R14DB"

dbPwd="R14DB"

Procedure

  1. Launch the following command in the command line.

    2. %WAS_HOME%\bin\ wsadmin -lang jython -f  MSSQLConfiguration.py

  2. Browse the administrative console to check if this step is correctly done. 
    3. NOTE: The property dbPwd is not correctly set, you have to run the administrative console to re-enter it manually as shown below.
  3. Click Security > Global security > Java Authentication and Authorization Service > J2C authentication data and specify Alias as Temenos Transact database MSSQL, User ID and Password.

  4. Click OK.

  5. Click Apply then Click Save.

Deploying TAFJ Application

TAFJ application deployment can be run automatically. The script is located at %TAFJ_HOME% \appserver\was\jython\TAFJapplicationDeployment.py

It executes the following actions:

  1. Deploy TAFJJEE_EAR.ear application.
  2. Before running it you have to define some parameters such as node, cell and server name to set the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file.  You must also define the tafjHome as root folder to locate the applications to be deployed. That is:

    tafjHome="C:/product/appserver/websphere/TAFJ"

  3. Launch the following command in the command line.

    wsadmin -lang jython -f  TAFJapplicationDeployment.py

  4. Stop and restart your server to start the applications.
  5. Type the stopServer <your_server_name> command in the command line.

  6. Type the startServer < your_server_name > command in the command line.

  7. Browse the administrative console to check if the application is correctly deployed and started.

ClosedDeploying TAFJ Application in Console Mode

You can also manually deploy or redeploy TAFJJEE_EAR.

Procedure

  1. In the console, click Applications > New Application > New Enterprise Application.
  2. Select local file deployment option and the TAFJJEE_EAR.ear file under the % TAF_HOME%\appserver folder. Click Next.

  3. Select Detailed - Show all installation options and parameters and click Next.
  4. In the Install New Application wizard, do the following steps:
    1. Step 1 Select installation options: Click Next with default values.
    2. Step 2 Map modules to servers: Click Next with default values.
    3. Step 3 Provide JSP reloading options for Web modules: Click Next with default values.
    4. Step 4 Map shared libraries: Add TAFJ shared libraries and Temenos Transact shared libraries.

    5. Repeat steps a to c for the other steps present in the Install New Application wizard and finish the wizard.
  1. Validate at the end of the installation processing that the TAFJJEE_EAR.ear application was installed successfully.
  2. Click Save.

Logging Configuration

Since PB201607 the default logging API being used is Log4j 2. To keep using former Log4j 1.2 with existing TAFJTrace configuration, you need to do the following modifications in your TAFJ shared lib:

  1. Delete $TAFJ_HOME/lib/log4j-api.jar and $TAFJ_HOME/lib/log4j-api.jar 
  2. Copy $TAFJ_HOME/3rdParty/logging/log4j12/log4j.jar to $TAFJ_HOME/lib/log4j.jar
  3. Provide as a server JVM argument the logging API to use.

    -Dtemenos.log.api=LOG4J

ClosedAlternative

TAFJ can also be configured to use SLF4J instead of the default log4j 2 provided configuration. You need to do the following modifications to the TAFJ shared lib to use provided SLF4J version and the desired SLF4J to back-end bridge (SLF4J + Log4j 1.2):

  1. Delete $TAFJ_HOME/lib/log4j-api.jar and $TAFJ_HOME/lib/log4j-api.jar 
  2. Copy the following JARs:
    • $TAFJ_HOME/3rdParty/logging/slf4j/slf4j-api.jar to $TAFJ_HOME/lib/slf4j-api.jar
    • $TAFJ_HOME/3rdParty/logging/slf4j/slf4j-log4j12.jar to $TAFJ_HOME/lib/slf4j-log4j12.jar
    • $TAFJ_HOME/3rdParty/logging/log4j12/log4j.jar to $TAFJ_HOME/lib/log4j.jar
  1. Provide as a server JVM argument the logging api to use.

    -Dtemenos.log.api=LOG4J

    and the logging back-end to use

    -Dtemenos.log.backend=LOG4J

NOTE: Please refer to standalone documentation for more information about logging.

TAFJ Servlets

The TAFJJEE_EAR.ear file sets MDB (TAFJJEE_MDB.jar) and EJB (TAFJJEE_EJB.jar) to read message from JMS Queues, call Temenos Transact and publish response in reply queues.

It also contains a WAR file to deploy helper servlet.

http://localhost:8080/TAFJEE

NOTE: For more information, please refer to the TAFJ-AS TAFJ documentation.
ClosedtDiag Servlet

TAFJJEE_WAR_TAFJ contains a servlet which allows you to get details about TAFJ installation.

http://localhost:8080/TAFJEE/tDiag

ClosedtShow Servlet

TAFJJEE_WAR_TAFJ contains a servlet which allows you to get compilation details about a specific routine

http://localhost:8080/TAFJEE/tShow

The screen captures below show the details about JF.INITIALISE.CONNECTION.

ClosedExecute Servlet

TAFJJEE_WAR_TAFJ contains a servlet which allows you to post message to the JMS queue t24ExeqQueue.

http://localhost:8080/TAFJEE/Execute

That is to post START.TSM submit START.TSM in the form.

Remark: The following properties need to be set correctly to run TAFJ within an application server context:

temn.tafj.runtime.phantom.as.process = false

ClosedOther TAFJEE functionalities

TAFJEE application offers many other functionalities like monitoring, changing log level, como viewer, etc.

NOTE: For more information, see TAFJ AS documentation for detailed information.

Deploying Temenos Transact Application

Temenos Transact application – BrowserWeb.war deployment can be run automatically.

The script is located at %TAFJ_HOME% \appserver\was\jython\ T24applicationDeployment.py. On executing this script, it deploys Browserweb.war.

Before running it you have to define some parameters such as node, cell and server name to set the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file.  You must also define the browserWebHome as root folder to locate the Browserweb.war to be deployed. That is:

browserWebHome="C:/product/appserver/websphere/TAFJ/appserver"

Procedure

  1. Launch the following command in the command line.wsadmin -lang jython -f  T24applicationDeployment.py

  2. Stop and restart your server to start the application. You can then browse the administrative console to check it has been correctly deployed and started.
ClosedDeploying Temenos Transact Application in Console Mode

You can also manually deploy or redeploy BrowserWeb.war.

Procedure

  1. With the admin console under Applications\New Application\New Enterprise Application, select local file deployment option and the browser.war file. Click Next.

  2. Select Detailed - Show all installation options and parameters and click Next.
  3. In the Install New Application wizard, do the following steps:
    1. Step 1 Select installation options: Click Next with default values.
    2. Step 2 Map modules to servers: Click Next with default values.
    3. Step 3 Provide JSP reloading options for Web modules: Click Next with default values.
    4. Step 4 Map shared libraries: Click Next with default values.
    5. Step 5 Map shared library relationships: Click Next with default values.
    6. Step 6 Map resource references to resources: Bind jms/jmsConnectionFactory    to jms/t24ConnectionFactory, queue/t24OFSQueue to jms/t24OFSQueue and queue/t24OFSReplyQueue to jms/t24OFSReplyQueue.

    7. Step 7 Map virtual hosts for Web modules: Click Next with default values.
    8. Step 8 Map context roots for Web modules: Set Context Root to /BrowserWeb.

    9. Step 9 Summary: Click Next with default values.
  4. Click Next and Finish.
  5. In the Enterprise Applications page, select BrowserWeb application and click Start.
  6. Browser http://IP_Add:9080/BrowserWeb/servlet/BrowserServlet, where IP_Add is the IP address of the WebSphere server.
Expand/Collapse
Share
Print

In this topic

Copyright © 2020- Temenos Headquarters SA

Published on :
Friday, October 22, 2021 3:41:24 PM IST

Feedback
x